Skip to content

Drop paratest conflict, require pest ^5.3.4 - #8

Merged
jayjfletcher merged 1 commit into
mainfrom
ring-master/2026-10-27-1057-drop-paratest-conflict
Oct 28, 2026
Merged

jayjfletcher merged 1 commit into
mainfrom
ring-master/2026-10-27-1057-drop-paratest-conflict

Conversation

@jayjfletcher

Copy link
Copy Markdown
Member

Closes #7

Removes the brianium/paratest >=7.26.1 conflict and raises pestphp/pest to ^5.3.4. Pest 5.3.2+ requires paratest ^7.26.1 and fixes the WrapperWorker::__construct call, so the conflict made every dependent package unresolvable.

Verification: composer test passes (phpstan 0 errors, pint, type coverage 100%, pest 82/82 in parallel with paratest 7.27.4). composer.lock is gitignored, so it is not in the diff. CI fresh resolve is proven by this PR's run.

Follow-up: Keen has the same conflict in its own composer.json and needs the same change after this lands.

🤖 Generated with Claude Code

Pest 5.3.2+ requires paratest ^7.26.1 and fixes the WrapperWorker
constructor call, so the conflict block made dependents unresolvable.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@jayjfletcher
jayjfletcher merged commit 924703f into main Oct 28, 2026
4 checks passed
@jayjfletcher
jayjfletcher deleted the ring-master/2026-10-27-1057-drop-paratest-conflict branch October 28, 2026 00:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Drop paratest conflict, require pest ^5.3.4

1 participant